Require domain separation for SignerDecrypter signature payloads using the StandardCapabilityAccount#1578
Conversation
✅ API Diff Results - No breaking changes |
Co-authored-by: Jordan Krage <jmank88@gmail.com>
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 2.
| Benchmark suite | Current: 3d2884e | Previous: 60798d1 | Ratio |
|---|---|---|---|
BenchmarkKeystore_Sign/nop/in-process |
731.8 ns/op |
352.2 ns/op |
2.08 |
This comment was automatically generated by workflow using github-action-benchmark.
|
@jmank88 interesting to see: #1578 (review). I guess |
Oh, wasn't that there with the last version too? The internals look equivalent. |
The benchmarks test passed on the commit before the hasPrefix change 🤷 |
This ensures that users of the
StandardCapabilityAccountaccount for theSignerDecryptercomponent domain separate their payloads using the recommendedMakePeerIDSignatureDomainSeparatedPayloadhelper function from libocr.Also, bumps libocr.